This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
We have been looking at updating to BES10, and I recently installed the BES10 service on one of our Domino Servers. After first installing BES10, I had some hurdles to overcome, which ended up with me uninstalling BES10, deleting all the applicable install folders, and starting from scratch.
Our BES10 is up and running, and BlackBerry Support has been phenomenal getting us as far as we are. However, I think we might have a unique environment, although we are using a suggested tip from the Domino Guru (http://www.dominoguru.com/pages/noupgradetraveler852viacrosscerts.html). We are running our Traveler Server (8.5.3 Upgrade Pack 2) in it's own Domino Domain, in the DMZ, and using Directory Assistance against a replica of our primary Domain's Domino Directory.
One of the requirements we've run up against is that the BES10 server must be able to connect to the Traveler server. As I understand it, BES10 uses the user's credentials (shortname/internet password) to authenticate and activate the Active Sync on the Traveler Server.
In our testing, I can create a user in the BES10 Administrator Console, then activate the Z10. The PIN is updated on BES10, meaning the device is communicating to the BES10 server. Since the BES10 can't reach across to the Traveler server, I am unable to get PIM sync working (no mail, no calendar, no contacts...nothing). In our environment, our internal network can't reach outside, then right back in to the server in the DMZ. Additionally we are unable to reach the Traveler Server via its Private, Internal IP Address.
Does ActiveSync work on the Blackberry Device (Z10, in our case)? Yes! If I don't authenticate/activate the device through the BES10, I can manually use the Advanced settings on the device, providing it my short name, internet password, and public URL for the Traveler server. This activation is almost the same as connecting an iPhone to Travler, as Mail, Calendar, and Contacts are synching, but I am not "under BES10 Control". I am basically a rogue device on the Traveler server, without MDM (Mobile Device Management).
One thing I had to do the 2nd go around was to reassign the secure port on the BDS (BlackBerry Device Service) install. The install defaults to 433. Rather than create a conflict, I prepended a different number to the port (ie. 57433). The preliminary install defaulted to 433, and I was unable to connect to the BlackBerry Administration Console except on the Server where the application was installed. Now I am able to connect and administer from other PCs within our environment.
Because we are still working through the hiccups of the BDS install, the UDS and other components have not been installed. Our ultimate goal was to set the BDS, the UDS, and BMS such that we could manage new BlackBerry Devices and iPhones from the same server. However, my peer found this article which seems to indicate setting up a single, multi-function server may be a challenge, and recommends 3 separate servers: http://darelmona.com/Comm.Tech/blackberry-bes-10-review/
I'm still in the testing portion, and trying to work out a manner to allow BES10 to communicate to Traveler. Ultimately we'd like to activate a Z10 via the BES10, for device management, and link the device to Traveler for synching mail, calendar, and contacts.
Brian
Feedback response number WEBB96LPP8 created by ~Julia Quetjipytexings on 04/09/2013
My experience with BES10
Return to top
. . My experience with BES10 (~Julia Quetjipy... 9.Apr.13) 
